systemd: enabling cherokee service as a `unit file`
Posted
by
Calvin Cheng
on Server Fault
See other posts from Server Fault
or by Calvin Cheng
Published on 2012-04-27T07:01:07Z
Indexed on
2012/09/22
15:39 UTC
Read the original article
Hit count: 331
So I am learning how to use systemd
to initialize my services automatically on server reboot. So of course, I first make sure I have systemd
and some optional systemd
related packages installed.
pacman -S systemd initscripts-systemd
Installation seems to go well and checking, I can see that systemd
and its dependency libsystemd
are installed. And the optional package initscripts-systemd
is also installed:-
[root@li280-195 ~]# pacman -Ss systemd
extra/libsystemd 44-5 [installed]
systemd client libraries
extra/systemd 44-5 [installed]
system and service manager
extra/systemd-sysvcompat 2-2
sysvinit compat symlinks for systemd
community/initscripts-systemd 20120412-1 [installed]
Arch specific systemd initialization/bootup scripts for systemd
community/systemd-arch-units 20120412-2
Arch specific Systemd unit files
Next, I ensure that systemd
is loaded up when my server reboots, via grub
in grub
's /boot/grub/menu.lst
file like this:-
kernel /boot/vmlinuz root=/dev/xvda ro init=/bin/systemd
Rebooting my server to check, all loads up well and I can check that systemd
is operational via:-
systemctl list-unit-files
However, I don't see my cherokee initialization script (which is simply created at /etc/rc.d/cherokee
when I installed cherokee earlier via pacman -S cherokee
) being listed as one of my unit files.
So the question is, how do I do that? How do I put my cherokee initialization script under systemd
's control?
© Server Fault or respective owner